Skip to main content

Discord Bot Hosting - Internal Procedures

Overview​

This guide covers the internal procedures for provisioning and managing Discord bot hosting services on our Pterodactyl panel.

Service Details​

We offer Discord bot hosting with Node.js, Python, and Java support on our Pterodactyl game/bot hosting panel.

Panel URL: Check password manager for panel URL

Plans:

  • Mini Wumpus - Entry level, good for most bots
  • Medium Wumpus - More resources
  • Large Wumpus - High-resource bots

Client Order Process (Overview)​

Clients order via our website:

  1. Select plan and billing cycle
  2. Choose bot language (Node.js, Python, Java)
  3. Enter "Server Name" (what they want bot called)
  4. Complete payment
  5. Order goes to manual review

For Team: Provisioning Procedure​

1. Order Review​

Check these details:

  • Payment confirmed in WHMCS
  • Client selected correct plan
  • Bot language selected
  • Server name provided
  • Client account verified (not fraud)

2. Create Pterodactyl Server​

Access Pterodactyl Admin:

  1. Login to Pterodactyl admin panel
  2. Navigate to Servers \u2192 Create New

Server Configuration:

Server Name: [Client's chosen name]
Owner: [Client's email or existing Pterodactyl account]
Description: Discord Bot - [Client Name]

Location: Select available node
Egg: Discord Bot (Node.js / Python / Java based on order)

Resources:
- Allocate according to plan (CPU, RAM, Disk)
- Set limits per plan tier

Startup: Use default Discord bot egg startup

Allocation:

  • Assign primary network allocation
  • Bot typically doesn't need additional ports

3. Panel Account Creation​

If client doesn't have Pterodactyl account:

  1. Create user in Pterodactyl: Users \u2192 Create New
  2. Enter client's email
  3. Username: Usually client's name or domain
  4. Password: Generate secure password
  5. Send email with login credentials

If client already has account:

  • Assign new server to existing account

4. Welcome Email​

Send after provisioning:

Subject: Your Discord Bot Hosting Server is Ready!

Hi [Client Name],

Your Discord Bot Hosting server has been provisioned and is ready to use!

Panel Access:
URL: [Panel URL]
Username: [Username or Email]
Password: [Password if new account]

Server Name: [Server Name]
Plan: [Plan Name]
Language: [Node.js/Python/Java]

Getting Started:
1. Login to the panel
2. Go to "Files" to upload your bot files
3. Click "Console" to view bot output
4. Click "Start" to run your bot

Support:
If you need help, please open a ticket at https://portal.alfieweb.com/submitticket.php

Documentation: [Link to bot hosting docs if available]

Best regards,
Alfie Web Solutions Team

5. Post-Provisioning​

  • Update order status in WHMCS to "Active"
  • Add server details to client notes
  • Test server starts correctly
  • Monitor initial setup for issues

Optional Services​

Pre-configured Modmail/Ticket Bot​

Additional charge: £2.50

If client requests pre-configuration:

  1. Verify payment for additional service
  2. Install bot files (Modmail or Ticket bot)
  3. Configure basic settings
  4. Provide client with bot token setup instructions
  5. Test bot functionality
  6. Document configuration in handover notes

Common Bots:

  • Discord Modmail
  • Ticket Tool
  • Custom client bot

Managing Existing Servers​

Upgrading Plan​

  1. Modify server in Pterodactyl
  2. Update resource allocations
  3. Restart server
  4. Update WHMCS service
  5. Notify client

Suspending Server​

Reasons for suspension:

  • Non-payment
  • Terms of service violation
  • Resource abuse

Action:

  1. Suspend in WHMCS
  2. Suspend server in Pterodactyl (or power off)
  3. Send suspension notice
  4. Document reason

Canceling/Deleting Server​

When service ends:

  1. Mark canceled in WHMCS
  2. Take backup of server files (if client requests)
  3. Delete server in Pterodactyl
  4. Confirm deletion to client
Data Loss

Deleting server is permanent! Always offer backup before deletion.

Troubleshooting​

Client Can't Login to Panel​

Check:

  • Using correct panel URL
  • Account exists in Pterodactyl
  • Password correct
  • Account not locked
  • 2FA not enabled (unless they set it up)

Solution:

  • Reset password in Pterodactyl admin
  • Send new credentials via portal ticket

Bot Won't Start​

Common causes:

  • Missing dependencies
  • Incorrect startup command
  • Bot token invalid
  • Code errors

Debugging:

  1. Check console output for errors
  2. Verify startup command in server settings
  3. Check bot token is valid
  4. Review file structure
  5. Check resource limits not exceeded

Guide client to:

  • Check console for error messages
  • Verify all required files uploaded
  • Confirm bot token is correct
  • Check dependencies installed

Bot Keeps Crashing​

Causes:

  • Code errors
  • Out of memory
  • Hitting rate limits
  • Discord API issues

Solution:

  1. Check console logs
  2. Verify resource usage (RAM, CPU)
  3. Consider plan upgrade if hitting limits
  4. Review bot code for issues

File Upload Issues​

Common issues:

  • File too large
  • Disk space exceeded
  • Permission errors

Solution:

  • Check plan disk limit
  • Use SFTP for large uploads
  • Verify file permissions
  • Clear old files if needed

Server Using Too Many Resources​

If server consuming excessive resources:

  1. Check what's running (console)
  2. Contact client about usage
  3. Suggest optimization or upgrade
  4. Consider suspension if abuse

Client Common Questions​

Q: "How do I upload my bot?"

  • Panel \u2192 Files \u2192 Upload
  • Or use SFTP (provide SFTP details from panel)

Q: "How do I get bot token?"

Q: "Bot shows offline in Discord"

  • Check if server is running (panel shows "Running")
  • Verify bot token is correct
  • Check console for errors
  • Ensure bot has proper intents enabled

Q: "Can I restart bot automatically?"

  • Yes, enable "Restart on Crash" in server settings

Q: "How do I install packages (npm/pip)?"

  • Use console or SFTP
  • Node: npm install package-name
  • Python: pip install package-name
  • May need to edit startup command

Node Setup Tips​

For Node.js bots:

  • Main file usually index.js or bot.js
  • Startup: node index.js
  • Install packages: npm install
  • Check package.json for dependencies

For Python bots:

  • Main file usually main.py or bot.py
  • Startup: python main.py or python3 main.py
  • Install packages: pip install -r requirements.txt

For Java bots:

  • Usually .jar file
  • Startup: java -jar bot.jar
  • More complex, less common

Monitoring​

Regular checks:

  • Server uptime
  • Resource usage across all bot servers
  • Client tickets about bot issues
  • Node capacity and load

Performance issues:

  • If node overloaded, consider migrating servers
  • Monitor RAM and CPU usage
  • Check for abuse or poorly optimized bots

Best Practices​

  • Always backup before making changes
  • Test server starts after provisioning
  • Document any custom configurations
  • Keep client informed of maintenance
  • Monitor resource usage
  • Respond quickly to bot hosting issues (often urgent for clients)

Quick Reference​

| Task | Action |\n|------|--------|\n| Create server | Pterodactyl \u2192 Servers \u2192 Create |\n| Reset password | Pterodactyl \u2192 Users \u2192 Edit user |\n| Suspend server | Power off or suspend in panel |\n| View logs | Server console in Pterodactyl |\n| Change resources | Edit server allocations |\n| Delete server | Delete in Pterodactyl (backup first!) |\n\n## Support Escalation

When to escalate:

  • Pterodactyl panel issues
  • Node/server infrastructure problems
  • Complex bot debugging beyond basic support
  • Suspected abuse or security issues

Contact: Tom or Alfie for infrastructure issues